Internet Surfer 2.0/Internet Surfer 2.0 (Wayzata Technology) (1996).iso/pc/text/mac/faqs.553

Text File | 1996-02-12 | 29KB | 594 lines

Frequently Asked Questions (FAQS);faqs.553



Also:
    In addition, these commercial products (unsorted) are available in
final or prerelease form [the * following the product name indicates that the
product is known to allow the designer to specify for each widget whether a
particular resource is hard-coded or written to an application defaults file,
for at least one form of output]. Some are much more than user-interface tools;
some are full user interface management systems:

Product Name        Look/Feel    Code Output        Vendor
HP Interface        Motif 1.1    C(Xm)            HP/Visual Edge
 Architect/ UIMX
OPEN LOOK Express    OPEN LOOK    C(Xol+ helper lib)    AT&T/Visual Edge
UIMX 2.0 *        Motif 1.1    C(Xm + helper code)    Visual Edge
                                514-332-6430
                                & distributors
VUIT 2.0        Motif 1.1    C/UIL[r/w]        DEC
                                (1-800-DIGITAL)
X-Designer 1.1 *    Motif 1.1    C(Xm); C/UIL        Imperial
                                Software
                                Technology, Ltd
                                ([phone])
                                [e-mail]
XFaceMaker2 (XFM2) *     Motif 1.0    C;C/script (C-like procedural
                    language);C/UIL
                                 NSL
                            (33 1 43 36 77 50)
                            [e-mail]
Builder Xcessory 2.0 *    Motif 1.1    C(Xm); C/UIL[r/w]    ICS
                                (617-621-0060)
                                [e-mail]
XBUILD 1.1 *        Motif 1.0    C(Xm); C/UIL         Nixdorf
                                (617-864-0066)
                            [e-mail]
iXBUILD            Motif 1.1    C(Xm); C/UIL        iXOS Software
                                [e-mail]
                                089/461005-69
TeleUSE 2.1 *        Motif 1.1.5    C(Xm); C/UIL[r/w]
                                Telesoft
                                (619-457-2700)
                            [e-mail]
ezX 3.2            Motif 1.1    C(Xm +helper lib);C/UIL;Ada
                                Sunrise
                                (401-847-7868)
                                [e-mail]
Snapix            Motif        C/Xm            ADNT
                                [phone]
OpenWindows Developers    OPEN LOOK     GIL [-> C/XView]    Sun
Guide 3.0                GIL [-> C++/XView]
                    GIL [-> C/OLIT]
                    GIL [-> C/PostScript for TNT]
ExoCode/SXM        Motif        C(Xm)            Expert Object
ExoCode/Plus        OPEN LOOK    XView            708-676-5555
TAE+            Xw;Motif    C(Xw,Xm); C/TCL (TAE Control Language,
                    like UIL[needs helper library]);
                    VAX Fortran; Ada
                                Nasa Goddard
                                [phone]
MOB, XSculptor            Motif; OpenLook    C/Xm,UIL; C/Xol        Kovi
                                408-982-3840
PSM            PM, MSW 3.0,    C/UIL            Lancorp
            Motif 1.1.2,Mac                Pty Ltd.
                                [phone]
                                Fax:  [phone]
                                (Australia)
MOTIFATION        Motif 1.0|1.1.2    C(Xm)            AKA EDV
                            +49 (0) 234/33397-0
                            +49 (0) 234/33397-40 fax
UIB            Open Look/Motif    C++(OI)            ParcPlace
                                [phone]

Look for magazine reviews for more complete comparisons of meta-file formats,
documentation, real ease-of-use, etc; Unix World and Unix Review often carry
articles.

    In addition, Neuron Data (1 415 321-4488) makes Open Interface, a
window-system-independent object toolkit which supports interfaces which are
or resemble (supersets of) Mac, Windows, and Motif and Open Look; the package
includes an interface builder.

       In addition, the GRAMMI builder supports the development of Ada/X
applications using its own set of objects which are planned to have a Motif
look.  GRAMMI is written in Ada and generates Ada specs and stub bodies.
(1-800-GRAMMI-1).

    In addition, these non-WYSIWYG but related products may help for goals
of rapid prototyping of the application interface:

    WCL: the Widget Creation Library. Basically describes the widget
hierarchy and actions in a resources file; available from fine archive servers
everywhere, including devvax.jpl.nasa.gov (128.149.1.143) in pub/. Wcl provides
a very thin layer over Xt without any internal tweaking. 2.03 became available
11/92; version 2.04 will be available before 12/16/92.
    WINTERP: an Xlisp-based Motif toolkit allows for interpretive
programming. The copy on the R4 tape is outdated; get a copy off export or
email to [e-mail].
    The Serpent UIMS permits the building of user-interfaces without
specific knowledge of coding but with an understanding of attributes being set
on a particular [Motif] widget.  Beta Release 1.2 is available from
ftp.sei.cmu.edu (128.237.1.13) and can be found in /pub/serpent.  Serpent is
also available on export.lcs.mit.edu (18.24.0.11) in /contrib/serpent. Email
questions can go to [e-mail]. A commercial version of Serpent is
available as "Agora" from ASET, 221 Woodhaven Drive, Pittsburgh, PA 15228.
    Garnet is a Common Lisp-based GUI toolkit. Information is available
from [e-mail].
    MetaCard is a hypertext/Rapid Application Development environment
similar to Apple/Claris Corporation's HyperCard ([e-mail]). MetaCard
is available via anonymous FTP from ftp.metacard.com, csn.org, or
128.138.213.21.

----------------------------------------------------------------------
Subject:  87)  Where can I find X tools callable from shell scripts?
I want to have a shell script pop up menus and yes/no dialog boxes if the user
is running X.

    Several tools in the R3 contrib/ area were developed to satisfy these
needs: yorn pops up a yes/no box, xmessage displays a string, etc. There are
several versions of these tools; few, if any, have made it to the R4 contrib/
area, though they may still be available on various archive sites.
    In addition, Richard Hesketh ([e-mail]) has posted the xmenu
package to comp.sources.x ("v08i008: xmenu") for 1-of-n choices.  [7/90]
    Two versions of XPrompt have been posted to comp.sources.x, the latter
being an unauthorized rewrite. [R. Forsman ([e-mail]), 1/91]
    There is a version of XMenu available from comp.sources.x; it is
being worked on and will likely be re-released.
    xp-1.1.tar.Z, xpick-1.0.tar.Z and xzap-1.0.tar.Z on export's contrib/
are tools by [e-mail] which act as X versions of the
simple display and choice-making tools in K&P. [4/92]

----------------------------------------------------------------------
Subject:  88)  Where can I get an X-based debugger?

    xdbx, an X interface to the dbx debugger, is available via ftp from
export. The current [1/91] version is 2.1 patchlevel 2.
    An X interface to gdb called xxgdb is more like xdbx 2.1.2. It is part
of comp.sources.x volume 11 [2/91].
    mxgdb is a Motif interface to gdb by Jim Tsillas
([e-mail]); version 1.1.3 was posted to alt.sources 2/92.
Previous versions are on export.
    UPS is a source-level debugger which runs under the X11 and SunView
window systems on Sun and DEC platforms. It is available from export
(18.24.0.11) as contrib/ups-2.45.tar.Z and unix.hensa.ac.uk (129.12.21.7) in
/pub/misc/unix/ups (or try mail to [e-mail]). [10/92]

Also:
    MIPS produces a highly-customizable (WCL-based) Visual Debugger.
    You should be able to use Sun's dbxtool with its X11/NeWS server.
    The CodeCenter (617-498-3000) source-level debugger, available on most
major platforms, includes an X-based interface.
    AT&T offers the eXamine Graphical Interface, an X11 interface to dbx
and C++ dbx for Sun3 and Sun4 and sdb and sdb++ for 386 and 3B2 platforms. Call
1-508-960-1997 or contact [e-mail] for more information.
        Solbourne ([phone]) offers PDB, its X-based debugger for C, C++
and Fortran.  PDB uses the OI toolkit and runs in either Open Look or Motif
mode.
    SCO ([e-mail]) offers dbXtra as part of several development
systems.

----------------------------------------------------------------------
Subject:  89)  How can I "tee" an X program identically to several displays?

    There are several protocol multiplexer tools which provide for the
simultaneous display of X clients on any number of machines.
    XMX (an X Protocol Multiplexor) is available from wilma.cs.brown.edu
(128.148.31.66) as pub/xmx.tar.Z It works independently of the server and does
not affect the application being shared; it was developed for use in the
electronic classroom.
    XTV is a conference program which can be used to duplicate the
"chalkboard" on several displays. Release 1 is available on the X11R5 contrib
tapes; a more recent version is on ftp.cs.odu.edu as pub/wahab/XTV.r2.tar.Z.
    SHX from Michael Altenhofen of Digital Equipment GmbH CEC Karlsruhe
also does this; it is a "WYSIWIS" (What You See Is What I See) package in the
context of a computer-based learning/training tool to provide online help from
remote tutors but is also useful for general window sharing. Information:
[e-mail].  SHX can be found on export and
        gatekeeper.dec.com:/pub/X11/contrib/shX.tar.Z,
        crl.dec.com:/pub/X11/contrib/shX.tar.Z
Modifications to SHX for color mapping and private color allocation by
Mark J. Handley ([e-mail]) are on cs.ucl.ac.uk in
car/shX.car.tar.Z.
    XTrap is implemented as a server/library extension and can be used
to record and then replay an x session. It is available as:
        gatekeeper.dec.com      pub/X11/contrib/XTrap_v31.tar.Z
        export.lcs.mit.edu      contrib/XTrap_v31.tar.Z
    wscrawl can be used as a "multi-person paint program". It's available
on sax.stanford.edu as wscrawl.shar.Z.
    Shdr implements a simple shared whiteboard, without a chalk-passing
mechanism. It's available on parcftp.xerox.com as pub/europarc/shdr.tar.Z.

Also of use:
        Hewlett-Packard Co. has a commercial product, "HP SharedX" which works
under HP-UX currently on their 300, 400, and 700 series workstations and their
HP 700/RX X Stations.  Machines receiving shared windows can be any X server.
HP SharedX consists of a server extensions and a Motif based user interface
process.  Contact your local HP sales rep. for more information.
    IBM offers a commercial product.
    Sun offers multi-user confering software called ShowMe.
    InSoft (Mechanicsburg, PA, USA) offers multi-user confering software
called Communique.

[Thanks in part to [e-mail] (Tim Scott), 5/91, and to Peter Cigehn
([e-mail]), 8/92 ]

----------------------------------------------------------------------
Subject:  90)  TOPIC: BUILDING THE X DISTRIBUTION [topic needs updating to R5]
----------------------------------------------------------------------
Subject:  91)  What's a good source of information on configuring the X build?

    This FAQ includes information on a number of "gotchas" that can bite
you on particular system. However, the best source of general information on
building the X11 release is found in the Release Notes. The file is bundled
separately from the rest of the release, so if it's become separated from your
sources you can FTP another copy separately: the file RELNOTES.[ms,PS,TXT] at
the top of the distribution. The file RELNOTES is also available from the
xstuff mail server.
    In addition, O'Reilly & Associates's Volume 8 on X Administration
includes information on configuring and building X.

----------------------------------------------------------------------
Subject:  92)  Why doesn't my Sun with a cg6 work with R5?

    Apparently gcc is the problem; it seems to produce fine code for all
Sun displays except for the cgsix. The new sunGX.o distributed with fix-07
may fix the problem (note: not known to work on Solaris).

----------------------------------------------------------------------
Subject:  93)  Why doesn't my Sun with SunOS 4.1 know about _dlsym, etc.?

    If you get errors with _dlsym _dlopen _dlclose undefined, link with
libdl.a.  Add "-ldl" to your and eventually your site.def.  You may want to
surround it with "-Bstatic -ldl -Bdynamic" if you add it to the EXTRA_LIBRARIES
variable, since "syslibs" get added after EXTRA_LIBRARIES on the eventual
compilation command; otherwise you may not have a shared libdl.  (Or compile
the stubs shared.)

[thanks to Joe Backo ([e-mail]), 12/91]

----------------------------------------------------------------------
Subject:  94)  What is this strange problem building X clients on SunOS 4.1.2?

    In SunOS 4.1.2 Sun fixed a shared-library bug in ld which conflicts
with the way X11R4 builds the shared Xmu library, causing these symbols to be
undefined when building some X11 clients:
    _get_wmShellWidgetClass
    _get_applicationShellWidgetClass
Compiling "-Bstatic -lXmu -Bdynamic" appears to work.

To solve the problem if you are using OpenWindows 3.0 (X11R4-based Xt), please
contact your local Sun office and request the following patches:

Patch i.d.      Description
100512-02       4.1.x OpenWindows 3.0 libXt Jumbo patch
100573-03       4.1.x OpenWindows 3.0 undefined symbols when using
                        shared libXmu

[Greg Earle, [e-mail]; 7/92]

----------------------------------------------------------------------
Subject:  95)  Why can't gcc compile X11R4 on my SPARC?
I used gcc to compile the whole distribution, but I get several segmentation
faults when running X.

    Note first that gcc on RISC machines does not necessarily result in
any performance increase; it certainly is not as noticeable as it is on the
680x0 or VAX platforms.

    Here is the problem: gcc and cc use incompatible methods of passing
structures as arguments and returning them as function values, so when
gcc-compiled parts of X are linked with Sun-supplied functions that pass or
return structs, run-time errors occur.  Affected programs include rgb and
the server.

    This is from the GCC manual:

    On the Sparc, GNU CC uses an incompatible calling convention for
    structures.  It passes them by including their contents in the argument
    list, whereas the standard compiler passes them effectively by
    reference.

    This really ought to be fixed, but such calling conventions are not yet
    supported in GNU CC, so it isn't straightforward to fix it.

    The convention for structure returning is also incompatible, and
    `-fpcc-struct-return' does not help.

You can duck the problem either by using cc throughout or by using it for just
the routines which cause incompatibilities; the problem cannot be solved with
compilation flags.

    Files which need to be compiled using cc include:
        server/os/4.2bsd/oscolor.c
        rgb/rgb.c

    In addition, several of the "inet_" functions use structs as args or
return values:
        clients/xhost/xhost.c
        clients/xauth/gethost.c.
Calls to inet_addr in /lib/CLX/socket.c and lib/X/XConnDis.c are possibly
harmless as they don't involve structs.

[collected by [e-mail] (Don Bashford); 8/90]

----------------------------------------------------------------------
Subject:  96)  What are these I/O errors running X built with gcc?
When I try to run xinit or the Xsun server I get the error
    "Getting interface configuration: Operation not supported on socket.
    Fatal server bug! no screens found."

    Running the gcc fixincludes script apparently didn't work. You can do
this simple test:

    #include <sys/ioctl.h>
    SIOCGIFCONF

Run that through cc -E and gcc -E.  The last line of output is the piece of
interest; it should be identical (modulo irrelevant differences like
whitespace).  If the gcc version has 'x' where the cc version has 'i', your
fixincludes run didn't work for some reason or other; go back to your gcc
sources and run `fixincludes`; then rebuild the X distribution. If they are
identical, try running a make clean in mit/server and rebuilding, just to make
sure everything gets compiled with the proper include files.

[courtesy der Mouse, [e-mail]; 9/90]

----------------------------------------------------------------------
Subject:  97)  What are these problems compiling X11R4 on the older Sun3?
In mit/server/ddx/sun/sunCG3C.c, we have found "missing" defines for
CG3AC_MONOLEN, CG3BC_MONOLEN, CG3AC_ENBLEN, CG3BC_ENBLEN. What should these be?

    The R4 Errata list distributed after X11R4 mentions that you can add
these lines to the file on older SunOS versions (e.g. 3.5) to compile:
        #define CG3AC_MONOLEN (128*1024)
        #define CG3AC_ENBLEN  CG3AC_MONOLEN
        #define CG3BC_MONOLEN CG3AC_MONOLEN
        #define CG3BC_ENBLEN  CG3AC_MONOLEN

    However, the Sun3 should not actually ever have the CG3 device, and so
references to it can be removed from mit/server/ddx/sun/sunInit.c and the
Imakefile.  [11/90]

----------------------------------------------------------------------
Subject:  98)  What are these problems compiling the X server on SunOS 4.1.1?
The file <sundev/cg6reg.h> isn't being found.

    Sun omitted <sundev/cg6reg.h> from SunOS 4.1.1. Remove the #include
from sunCG6C.c and replace it with the line
    #define CG6_VADDR_COLOR   0x70016000
The file has changed from earlier versions of SunOS and should not be copied
from another distribution.

----------------------------------------------------------------------
Subject:  99)  What are these problems using R4 shared libraries on SunOS 4?
All of the executables that I try to run have the following results:
    ld.so: libXmu.so.4: not found
or even:
    ld.so: call to undefined procedure __GetHostname from 0xf776a96c

    If you are building with shared libraries on a Sun, remember that you
need to run "ldconfig" as root after installing the shared libraries (if you've
installed X on a file-server, run it on the server's clients, too).  While
building and installing the distribution, you need to be careful to avoid
linking against any existing X shared libraries you might have (e.g. those
distributed with OpenWindows).  You should make sure you do not have
LD_LIBRARY_PATH set in your environment during the build or the installation.
If you are going to keep xterm and xload as setuid programs, please note that
the shared libraries must be installed in /usr/lib, /usr/local/lib, or
/usr/5lib for these programs to work (or else those programs must be linked
statically). [courtesy MIT X Consortium]
    Note also that the program mkfontdir is run as part of the build; it
attempts, however, to use the shared libraries before they have been installed.
You can avoid the errors by building mkfontdir statically (pass -Bstatic to
most C compilers).

----------------------------------------------------------------------
Subject: 100)  Can OLIT programs run with R5 Xt? (_XtQString undefined)

This is a bug in the OLIT.  _XtQString was an external symbol that existed in
X11R4 (upon which OW 3.0's libXt is based).  It wasn't documented and was
removed in X11R5 (MIT's guarantee of upward compatibility between the R4 and R5
libraries only applied to the documented interface).

A workaround is to temporarily set your LD_LIBRARY_PATH to point to the X11R5
Xt library that you linked the program against.

[10/92; from Barry Margolin ([e-mail])

----------------------------------------------------------------------
Subject: 101)  How do I get around the SunOS 4.1 security hole?

    There is a security problem with certain R4 clients (xterm and xload)
running under SunOS 4.1 that have been installed setuid root and are using
shared libraries; to avoid the problem, do one of these:
    1) make the program non-setuid. You should consult your system
administrator concerning protection of resources (e.g. ptys and /dev/kmem) used
by these programs, to make sure that you do not create additional security
problems at your site.
    2) relink the programs statically (using -Bstatic).
    3) install the libraries before linking and link with absolute paths
to the libraries.

[from [e-mail] (Bob Scheifler), 12/90]

The R5 version of xterm does this automatically by rebuilding xterm against the
newly-installed libraries when xterm is being installed; this prevents an suid
program from being built with libraries specified relatively. Note that this
may cause an inconvenience when doing the installation from NFS-mounted disks.
Xload has been rewritten to avoid the problem.

----------------------------------------------------------------------
Subject: 102)  TOPIC: BUILDING X PROGRAMS
----------------------------------------------------------------------
Subject: 103)  What is Imake?

    Imake is not a replacement for the make program; instead, it is a
makefile-generator that takes advantages of the include-file and macro-
processing capabilities of the C preprocessor cpp to generate makefiles
suitable for building software on a particular system. Although it is not
specific to X, the X release uses it to help solve a number of the
configuration issues that arise in making such a large system widely portable.
    Imake has a fairly steep learning curve, in part because the process by
which the system-specific configuration files, system-independent configuration
files, and individual Imakefiles are melded to produce a Makefile is not
obvious.
    There have been several different versions of imake; the R3, R4, and
R5 versions are different.

    You can obtain information on imake from these sources:
    - the R4 and R5 release notes and imake man page include information on
using Imake to build X
    - the R4 and R5 file mit/config/README also contains useful information
    - on the R4 tapes, contrib/doc/imake/imake.tex is Mark Moraes' R3/R4
guide to imake.
    - the R5 mit/doc/config/usenixws/paper.ms contains a paper by Jim
Fulton on an early version of Imake
    - Paul Dubois ([e-mail]) has written a useful
explanation of how Imake works and how to use it in configuring X for non-
supported systems; the document is available from ftp.primate.wisc.edu
in the directory ~ftp/pub/imake-stuff; look for config-X11R4.ms (troff) and
config-X11R4.ps (PostScript). Some supplemental appendices are nearby.
[7/91: document version is now 1.06]
    - see "System Administration - Imake: Friend of Foe?" by Dinah McNutt
in the November 1991 issue of SunExpert.
    - German readers should expect in June 1992 an article "Das Meta-Make
/ I make, you make / Schwerelos" by Rainer Klute in "iX
Multiuser-Multitasking-Magazin", directed at application programmers needing to
write Imakefiles. An English-language derivative of this article is in The
X Journal, issue 2:1.
    - The O'Reilly X Resource issue #2 contains Paul Davey's article on
demystifying Imake.
    - Alain Brossard's working document full of tips on Imake is in
sasun1.epfl.ch:pub/imakefile.1.Z.

[1/91;12/91;5/92;8/92]

----------------------------------------------------------------------
Subject: 104)  Where can I get imake?

    Versions are distributed with the R4 and R5 releases. An earlier
version is distributed with the X11R3 release; some third-party toolkits
redistribute versions of imake along with their own implementations of the
template and configuration files. There are no real standards for such
configuration files, although most *current* contributed software expects the
templates distributed with X11R5.
    export contains the R5 distribution unpacked, so you can pick up imake
without picking up the entire distribution.
    A stand-alone version of Imake, but one stemming from X11R5, is in
ftp.germany.eu.net:pub/X11/misc/imake/imake-pure.tar.Z (192.76.144.75).

----------------------------------------------------------------------
Subject: 105)  I have a program with an Imakefile but no Makefile. What to do?

    If you have R4 or R5 installed on your system, run "xmkmf". This is a
script which runs imake for you with the correct arguments. The output is a
Makefile configured for your system and based on the Imakefile. Then run make,
which will use that new Makefile to compile the program.

----------------------------------------------------------------------
Subject: 106)  Why can't I link to the Xlib shape routines?
When I try to compile certain programs, I get the following link error:
    Undefined:
    _XShapeQueryExtension
    _XShapeCombineMask

    These routines are actually part of the Shape Extension to X (SHAPE)
which was introduced in the MIT X11R4 distribution and allows non-rectangular
windows.  Like the other sample server extensions, the shape extension will
only run on a server which supports it.  Pre-X11R4 servers, as well as many
vendor-supplied servers, do not support the shape extension, in which case
they will display rectangular windows anyway.

    In order to use the shape extension, you must link to the library
libXext.a.  In the X11R4 distribution, this library and the associated includes
will be in the mit/extensions directory.  If you do not have these files, do
not despair:  many freeware programs which use the shape extension can also be
compiled without it by removing the -DSHAPE define from the Makefile; you can
probably do this and compile successfully against your older vendor-supplied X
libraries.

[from John B. Melby, [e-mail], 3/91]

----------------------------------------------------------------------

David B. Lewis                     [e-mail]

        "Just the FAQs, ma'am." -- Joe Friday
--
David B. Lewis        Temporarily at but not speaking for Visual, Inc.
day: [e-mail]    evening: [e-mail]
Xref: bloom-picayune.mit.edu comp.windows.x:61857 news.answers:4490
Newsgroups: comp.windows.x,news.answers
Path: bloom-picayune.mit.edu!enterpoop.mit.edu!eff!sol.ctr.columbia.edu!caen!uunet!visual!dbl
From: [e-mail] (David B. Lewis)
Subject: comp.windows.x Frequently Asked Questions (FAQ) 4/4
Message-ID: <[e-mail]>
Followup-To: poster
Summary: useful information about the X Window System
Reply-To: [e-mail] (X FAQ maintenance address)
Organization: Visual
Date: Tue, 8 Dec 92 14:54:05 GMT
Approved: [e-mail]
Expires: Sun, 03 Jan 1993 00:00:00 GMT
Lines: 1043

Archive-name: x-faq/part4
Last-modified: 1992/12/07

----------------------------------------------------------------------
Subject: 107)  What are these problems with "_XtInherit not found" on the Sun?
When I run a X program that I wrote on a SunOS 4.0.3 or 4.1 machine I get the
error "ld.so: symbol not found _XtInherit".

    What you are seeing is a side-effect of a kludge in the R4 libXt.a to
get Sun shared libraries working.  Apparently, you can't share a function that
is both called and compared, as _XtInherit is. This was handled by putting
_XtInherit in the same file as a function that is always used, thereby
guaranteeing that it would be loaded -- that is, in Initialize.c, where
XtToolkitInitialize() and XtInitialize() reside. These routines would normally
be called.

    You are probably seeing this error because your program is not a normal
Xt-based program and does not call XtToolkitInitialize() anywhere.
    1) it may be a program that uses Xt functions but never opens a
connection to the X server.  [OSF/Motif's 1.1.0 UIL had this problem; it called
XtMalloc() and other Xt functions.] The solution is to add the call to your
program; the function does not have to be executed, just linked in.
    2) alternatively, your program doesn't need any Xt functions and is
correct in not calling XtToolkitInitialize() -- it may be an Xlib or XView
program. In this case, you can remove -lXt from your link command.

    It should not be necessary to link the shared libraries statically,
although this will certainly solve the problem.

[from Jordan Hayes (now [e-mail]) and Danny Backx ([e-mail]);
11/90]

----------------------------------------------------------------------
Subject: 108)  Why can't I compile my R3 Xaw contrib programs under the new X?
I have a program that worked well under X11R3. When I try to link it under
the current version of X, I get this message:
    Undefined:
    _XtScrollBarSetThumb
    _XtTextSetInsertionPoint
    _XtTextReplace

    There were several name changes in the Athena widget set (in addition
to the header files moving into <X11/Xaw/>); these are mentioned in the R4
release notes. In this case, these functions are not really Xt functions but
are part of the Xaw text widget and so have been renamed from Xt* to Xaw*.
[10/90]

----------------------------------------------------------------------
Subject: 109)  TOPIC: PROGRAMMING PROBLEMS AND PUZZLES
----------------------------------------------------------------------
Subject: 110)  Why doesn't my program get the keystrokes I select for (sic)?

    The window manager controls how the input focus is transferred from one
window to another.  In order to get keystrokes, your program must ask the
window manager for the input focus.  To do this, you must set up what are
called "hints" for the window manager.  If your applications is Xlib-based, you
can use something like the following:

        XWMHints wmhints;
        ...
        wmhints.flags = InputHint;
        wmhints.input = True;
        XSetWMHints(dpy, window, &wmhints)

If your application is based on the Xt Intrinsics, you can set the XtNinput
resource to be True (as you probably want to in any case); if you don't have
source, you can start up the application with the resource '*input:True'.